Data processing apparatus and method for transferring workload between source and destination processing circuitry

ABSTRACT

In response to a transfer stimulus, performance of a processing workload is transferred from a source processing circuitry to a destination processing circuitry, in preparation for the source processing circuitry to be placed in a power saving condition following the transfer. To reduce the number of memory fetches required by the destination processing circuitry following the transfer, a cache of the source processing circuitry is maintained in a powered state for a snooping period. During the snooping period, cache snooping circuitry snoops data values in the source cache and retrieves the snoop data values for the destination processing circuitry.

BACKGROUND OF THE INVENTION

1. File of the Invention

The present invention relates to a data processing apparatus and methodfor switching a workload between first and second processing circuitry,and in particular to a technique for improving the processingperformance of the workload following the switch.

2. Description of the Prior Art

In modern data processing systems, the difference in performance demandbetween high intensity tasks such as games operation and low intensitytasks such as MP3 playback can exceed a ratio of 100:1. For a singleprocessor to be used for all tasks, that processor would have to be highperformance, but an axiom of processor micro-architecture is that highperformance processors are less energy efficient than low performanceprocessors. It is known to improve energy efficiency at the processorlevel using techniques such as Dynamic Voltage and Frequency Scaling(DVFS) or power gating to provide the processor with a range ofperformance levels and corresponding energy consumption characteristics.However, such techniques are generally becoming insufficient to allow asingle processor to take on tasks with such diverging performancerequirements.

Accordingly, consideration has been given to using multi-corearchitectures to provide an energy efficient system for the performanceof such diverse tasks. Whilst systems with multiple processor cores havebeen used for some time to increase performance by allowing thedifferent cores to operate in parallel on different tasks in order toincrease throughput, analysis as to how such systems could be used toimprove energy efficiency has been a relatively recent development.

The article “Towards Better Performance Per Watt in Virtual Environmentson Asymmetric Single-ISA Multi-Core Systems” by V Kumar et al, ACMSIGOPS Operating Systems Review, Volume 43, Issue 3 (July 2009),discusses Asymmetric Single Instruction Set Architecture (ASISA)multi-core systems, consisting of several cores using the sameinstruction set architecture (ISA) but differing in features,complexity, power consumption, and performance. In the paper, propertiesof virtualised workloads are studied to shed insight into how theseworkloads should be scheduled on ASISA systems in order to improveperformance and energy consumption. The paper identifies that certaintasks are more applicable to high frequency/performancemicro-architectures (typically computation intensive tasks), whileothers are more suited to lower frequency/performancemicro-architectures and as a side effect will consume less energy(typically input/output intensive tasks). Whilst such studies show howASISA systems might be used to run diverse tasks in an energy efficientmanner, it is still necessary to provide a mechanism for schedulingindividual tasks to the most appropriate processors. Such schedulingmanagement will typically place a significant burden on the operatingsystem.

The article “Single-ISA Heterogeneous Multi-Core Architectures: ThePotential for Processor Power Reduction” by R Kumar et al, Proceedingsof the 36^(th) International Symposium of Microarchitecture(MICRO-36'03) discusses a multi-core architecture where all coresexecute the same instruction set, but have different capabilities andperformance levels. At run time, system software evaluates the resourcerequirements of an application and chooses the core that can best meetthese requirements while minimising energy consumption. As discussed insection 2 of that paper, during an application's execution the operatingsystem software tries to match the application to the different cores,attempting to meet a defined objective function, for example aparticular performance requirement. In section 2.3, it is noted thatthere is a cost to switching cores, which necessitates restriction ofthe granularity of switching. A particular example is then discussedwhere, if the operating system decides a switch is in order, it powersup the new core, triggers a cache flush to save all dirty cache data toa shared memory structure, and then signals the new core to start at apredefined operating system entry point. The old core can then bepowered down, whilst the new core retrieves required data from memory.Such an approach is described in section 2.3 as allowing an applicationto be switched between cores by the operating system. The remainder ofthe paper then discusses how such switching may be performed dynamicallywithin a multi-core setting with the aim of reducing energy consumption.

Whilst the above paper discusses the potential for single-ISAheterogeneous multi-core architectures to provide energy consumptionreductions, it still requires the operating system to be provided withsufficient functionality to enable scheduling decisions for individualapplications to be made. The role of the operating system in thisrespect is made more complex when switching between processor instanceswith different architectural features. In this regard, it should benoted that the Alpha cores EV4 to EV8 considered in the paper are notfully ISA compatible, as discussed for example in the fifth paragraph ofsection 2.2.

Further, the paper does not address the problem that there is asignificant overhead involved in switching applications between cores,which can significantly reduce the benefits to be achieved from suchswitching. The overhead includes not just the time taken to perform theswitch during which no processor is performing the transferred workload,but also the penalty incurred by cache misses following the switch. Whenthe destination core starts performing the transferred processing, anycache provided in the destination core starts off containing no validdata, and so the destination core experiences cold start cache misses.This means that data has to be fetched from memory, which slowsprocessing performance and uses a significant amount of energy. Theperformance and energy efficiency recovers only once the destinationcache has been “warmed” by caching some of the data values stored inmemory. While the above paper by R. Kumar et al recognises the problemof cold-start cache misses at section 4.4, Kumar does not provide anysolution to this problem. The present technique seeks to improveprocessing performance following the switch to the destinationprocessor.

SUMMARY OF THE INVENTION

Viewed from a first aspect, the present invention provides a dataprocessing apparatus comprising:

first processing circuitry and second processing circuitry configured toperform a processing workload such that the processing workload isperformed by one of the first processing circuitry and the secondprocessing circuitry at a time;

power control circuitry for independently controlling the power supplyto the first processing circuitry and the second processing circuitry;

a workload transfer controller responsive to a transfer stimulus tocontrol a transfer of performance of the processing workload from asource processing circuitry to a destination processing circuitry priorto the source processing circuitry being placed in a power savingcondition by the power control circuitry, the source processingcircuitry being one of the first and second processing circuitry and thedestination processing circuitry being the other of the first and secondprocessing circuitry; wherein:

at least the source processing circuitry has a cache;

the power control circuitry is configured to maintain at least the cacheof the source processing circuitry in a powered condition during asnooping period following the start of performance of the transferredprocessing workload by the destination processing circuitry;

the data processing apparatus comprises cache snooping circuitryconfigured during the snooping period to snoop data values in the cacheof the source processing circuitry and to retrieve the snooped datavalues for the destination processing circuitry; and

the power control circuitry is configured to place said at least thecache of the source processing circuitry in the power saving conditionfollowing the end of the snooping period.

The data processing apparatus of the present invention has first andsecond processing circuitry, and at any time during processing, one ofthe first and second processing circuitry is performing a processingworkload. When a transfer stimulus occurs, performance of the processingworkload is transferred from a source processing circuitry (whichever ofthe first and second processing circuitry is currently performing theworkload at the time of receipt of the transfer stimulus) to adestination processing circuitry (the other of the first and secondprocessing circuitry), in preparation for the source processingcircuitry to be placed in a power saving condition. Irrespective of howthe transfer itself is achieved, the present technique improves theperformance level of the destination circuitry after the processingworkload has been transferred to the destination circuitry.

The present technique recognises that following the transfer, thedestination processing circuitry may require data values that werestored in a cache of the source processing circuitry before thetransfer. At least the cache of the source processing circuitry ismaintained in a powered condition for a finite period (the snoopingperiod) following the start of performance of the transferred processingworkload by the destination processing circuitry. Cache snoopingcircuitry snoops the data in the source cache during the snoopingperiod, and retrieves data on behalf of the destination processingcircuitry. By maintaining power to the source cache during the snoopingperiod, the destination processing circuitry has access to the data inthe source cache for an initial period of processing, thus avoiding theneed to fetch the data from memory. Since accesses to the source cacheare quicker and use less power than accesses to memory, the presenttechnique improves the performance level of the destination processingcircuitry, and the energy efficiency of the apparatus as a whole,following the transfer of the processing workload.

The present technique also recognises that the snooping of data in thissource cache is only useful for a finite period following the start ofperformance of the processing workload by the destination processingcircuitry. Eventually, the data in the source cache is no longerrelevant to the processing performed by the destination processingcircuitry. For example, the destination processing circuitry may beginprocessing another application that does not require the data from thesource cache, or the destination processing circuitry may have processedthe data such that an updated value, different to the value stored inthe source cache, is now being used. Therefore, at the end of thesnooping period, the cache snooping circuitry stops snooping data valuesfrom the source cache, and the power control circuitry is configured toplace at least the cache of the source processing circuitry in the powersaving condition, so as to save energy.

In summary, instead of powering down the source cache immediatelyfollowing the transfer of the processing workload to the destinationprocessing circuitry, the source cache is maintained in a powered statefor a snooping period during which the cache snooping circuitry cansnoop data values in the source cache and retrieve the snoop data valuesfor the destination processing circuitry. By reducing the number oftimes data is fetched from a memory, the performance level and energyefficiency is improved.

While the present application will generally describe the presenttechnique for the case where there are two processing circuits (thefirst and second processing circuitry), the data processing apparatusmay comprise further processing circuits and the technique may beapplied to the transfer of a processing workload between any two of theprocessing circuits. Moreover, each processing circuitry may include asingle processor core, or a plurality of processor cores.

The processing workload may include at least one processing applicationand at least one operating system for running the at least oneprocessing application. By treating the entire workload as a macroscopicentity that is performed on only one of the first and second processingcircuits at any particular point in time, the workload can be readilyswitched between the first and second processing circuits in a mannertransparent to the operating system. Such an approach addresses theearlier mentioned problems that result from using the operating systemto manage scheduling of applications to particular processing circuits.

The workload transfer controller may be configured during the transferto mask predetermined processor specific configuration information fromthe at least one operating system such that the transfer of the workloadis transparent to the at least one operating system. This means that theconfiguration of the operating system is simplified because theoperating system does not need to be aware of the differences betweenthe processor specific configuration information associated with thefirst processing circuitry and the processor specific configurationinformation associated with the second processing circuitry. Sinceprocessor-specific differences of the first and second processingcircuitry are masked from the operating system, then from the operatingsystem's perspective (and the perspective of any applications run by theoperating system), the workload is being run on a single hardwareplatform. Whether the workload is being run on the first processingcircuitry or the second processing circuitry, the operating system'sview of the hardware platform is the same. This makes it easier toconfigure the operating system and applications.

The workload transfer controller may comprise at least virtualisationsoftware logically separating the at least one operating system from thefirst processing circuitry and the second processing circuitry. Thevirtualisation software provides a level of abstraction in order to hidethe hardware configuration of the respective processing circuitries fromthe operating system, so that the operating system is unaware whichprocessing circuitry is performing the workload. Thus, the operatingsystem configuration can be simplified. The virtualisation software maycontrol the allocation of the processing workload to either the firstprocessing circuitry or the second processing circuitry.

The first processing circuitry may be architecturally compatible withthe second processing circuitry such that a processing workload to beperformed by the data processing apparatus can be performed on eitherthe first processing circuitry or the second processing circuitry. Thismeans that from an application perspective, the only difference betweenthe application running on the first processing circuitry and theapplication running on the second processing circuitry is theperformance level or energy efficiency achieved. There is no need for aninstruction set conversion between the first and second processingcircuitry. The entire processing workload including the operating systemand the applications being run by the operating system can betransferred backwards and forwards between the first and secondprocessing circuitry in a simple way.

The first processing circuitry may be micro-architecturally different tothe second processing circuitry such that performance of the firstprocessing circuitry is different from performance of the secondprocessing circuitry. The one of the first and second processingcircuitry having the higher performance level will generally consumemore energy than the other one of the first and second processingcircuitry. This means that the workload can be switched to the higherperformance processing circuitry if high performance processing isrequired (for example, when a gaming application is being performed). Onthe other hand, if low performance processing, such as MP3 playback, isbeing performed then the processing workload can be switched in itsentirety to the lower performance processing circuitry in order toimprove energy efficiency. Thus, by providing micro-architecturallydifferent processing circuits the performance of the processing workloadcan be optimised for performance or energy consumption depending on thenature of the workload to be performed.

The micro-architectural differences between the processing circuitriescan include, for example, different execution pipeline lengths ordifferent execution resources. Differences in pipeline length willtypically result in differences in operating frequency, which in turnwill have an effect on performance. Similarly, differences in executionresources will have an effect on processing throughput and henceperformance. For example, a processing circuit having wider executionresources will enable more information to be processed at any particularpoint in time, improving throughput. In addition, or alternatively, oneprocessing circuit may have more execution resources than the other, forexample, more arithmetic logic units (ALUs), which again will improvethroughput. As another example of different execution resources, anenergy efficient processing circuit may be provided with a simplein-order pipeline, whilst a higher performance processing circuit may beprovided with an out-of-order superscalar pipeline. Also, a higherperformance processing circuit could have branch prediction capabilitywhich speeds up processing by prefetching predicted branch targetsbefore the branch has been resolved, while a more energy efficientprocessing circuit could have no branch predictor. Suchmicro-architectural differences do not affect the ability of eacharchitecturally compatible processing circuit to perform the sameprocessing workload, but result in different levels of performance andenergy consumption when the respective processing circuits areperforming the processing workload.

The present technique may be used when only the source processingcircuitry has a cache. In this case, some memory accesses can be avoidedby the destination processing circuitry using the cache snoopingcircuitry to snoop the source cache during the snooping period.Following the end of the snooping period, all data would need to befetched from memory.

However, typically the destination processing circuitry would alsocomprise a cache, such that both the first and second processingcircuitry comprises a cache. In this case, the data values snooped bythe cache snooping circuitry and retrieved for the destinationprocessing circuitry by the cache snooping circuitry can be stored inthe cache of the destination processing circuitry to speed up futurereferences to the data.

In an embodiment, the power control circuitry may be configured to placethe source processing circuitry, other than the cache, in the powersaving condition during the snooping period, and to place the cache ofthe source processing circuitry in the power saving condition followingthe end of the snooping period. This reduces the power consumption ofthe data processing apparatus, since most of the source processingcircuitry can be powered down after the workload has been handed over tothe destination processor. Only the cache of source processing circuitryremains powered during the snooping period, to enable the cache snoopingcircuitry to retrieve the values stored in the source cache for thedestination processing circuitry.

In one embodiment, when the cache is part of a cache hierarchy in thesource processing circuitry, the snooped source cache can be maintainedin the powered condition during the snooping period while at least oneother cache in the cache hierarchy is in the power saving condition.

An example of this situation is when the source cache to be snooped is alevel two inclusive cache which is configured to store all of the datastored in any level one cache(s) of the cache hierarchy. In this case,the level two cache can be left in a powered state during the snoopingperiod to enable snooping from the cache snooping circuitry on behalf ofthe destination processing circuitry, while the level one cache(s) canbe powered down along with the rest of the source processing circuitry.

Alternatively, the power control circuitry may be configured to maintainthe source processing circuitry in the powered condition during thesnooping period and to place the entire source processing circuitry,including the cache, in the power saving condition following the end ofthe snooping period. Although leaving the source processing circuitrypowered during the snooping period increases power consumption, itreduces the complexity of the data processing apparatus sinceindependent power control to both the source cache and the remainder ofthe source processing circuitry is not required.

An example situation in which it may be desired to power the sourcecache and source processing circuitry together is when the cache of thesource processing circuitry to be snooped by the cache snoopingcircuitry is a level one cache. A level one cache may be too closelyintegrated to a processor core within the source processing circuitry tobe able to provide separate power control to the cache and the rest ofthe source processing circuitry. In this case, the entire sourceprocessing circuitry including the cache can be left powered during thesnooping period and powered down following the end of the snoopingperiod.

The source processing circuitry may be configured to perform a cleaningoperation on the source cache to write back any dirty data from thecache to a shared memory following the end of the snooping period andbefore the power control circuitry places the cache of the sourceprocessing circuitry in the power saving condition. By cleaning thesource cache before the cache is powered down, it is ensured that anydirty data, whose latest value has not yet been written back to memory,is not lost.

To save energy, it can be useful for the power control circuitry tomaintain the destination processing circuitry in the power savingcondition before the occurrence of the transfer stimulus. In this case,the power control circuitry can power up the destination processingcircuitry in response to the transfer stimulus.

The destination processing circuitry may be configured to invalidate thedestination cache before the destination processing circuitry startsperforming the transferred processing workload. For example, if thedestination processing circuitry has been in the power saving conditionprior to the transfer of the performance of the processing workload,then on powering up the destination processing circuitry the destinationcache can contain erroneous data. By invalidating the destination cachebefore the destination processing circuitry starts performing thetransferred processing workload, processing errors can be avoided.

To improve processing performance, the source processing circuitry maybe configured to continue performing the processing workload while thecache of the destination processing circuitry is being invalidated, andthe workload transfer controller may be configured to transfer theperformance of the processing workload to the destination processingcircuitry after the cache of the destination processing circuitry hasbeen invalidated. By allowing the source processing circuitry tocontinue performing the processing workload until the destinationprocessing circuitry is ready to start performing the processingworkload, the period of time during which neither processing circuitryis performing the processing workload is reduced and so the performancelevel of the processing workload is increased.

In one embodiment, the snooping period may begin when the destinationprocessing circuitry starts performing the processing workload.

The snooping period may end on the occurrence of any one of a set ofsnoop stop events comprising at least one snoop stop event. One or moresnoop stop events, indicating that it is no longer worth keeping thesource cache in the powered state, can trigger the cache snoopingcircuitry to end the snooping period. Typically, these events indicatethat the data in the source cache is no longer needed by the destinationprocessing circuitry.

The cache snooping circuitry may be configured to monitor whether any ofthe set of snoop stop events have occurred. For example, the cachesnooping circuitry may comprise performance counters for monitoring theprocessing of the destination processing circuitry and the data accessesperformed by the destination processing circuitry. Using the performancecounters, the cache snooping circuitry can analyse whether the data inthe source cache is still relevant to the processing being performed bythe destination processing circuitry. By configuring the cache snoopingcircuitry, rather than the destination processing circuitry, to monitorwhether any of the snoop stop events has occurred, the destinationprocessing circuitry can be left unaware of whether the source cache isstill being snooped. This makes the configuration of the destinationprocessing circuitry simpler.

The at least one snoop stop event may include an event that occurs thatwhen the percentage of snoops performed by the cache snooping circuitrythat result in a cache hit in the cache of the source processingcircuitry drops below a predetermined threshold level. If the percentageof cache hits in the source cache becomes low, then this indicates thatmany of the data values sought by the destination processing circuitryare no longer present in the source cache, and so the data in the sourcecache is not relevant to the destination processing circuitry.Therefore, power efficiency can be improved by ending the snoopingperiod and shutting down the source cache once the percentage of cachehits drops below a predetermined threshold level.

The at least one snoop stop event may also include an event that occurswhen the destination processing circuitry completes a predeterminednumber of processing transactions of a predetermined type following thetransfer of the processing workload. Although the destination processingcircuitry can access the data stored in the source cache via the cachesnooping circuitry, the destination processing circuitry will nottypically be able to update the values in the source cache. It can beexpected that, after a predetermined number of transactions havecompleted, the destination processing circuitry will have generated newvalues for some of the data originally stored in the source cache. Sincethe destination processing circuitry cannot write data to the sourcecache, the new data values would be stored in memory and/or adestination cache, which means that the original data values in thesource cache are no longer relevant to the destination processingcircuitry. Therefore, the completion of the predetermined number ofprocessing transactions of the predetermined type can indicate that thesource cache is no longer needed and so can trigger the end of thesnooping period. The predetermined type of processing transactions couldcomprise, for example, all transactions performed by the destinationprocessing circuitry or could comprise only cacheable transactions.

Another type of snoop stop event can be an event that occurs when apredetermined number of processing cycles have elapsed after thedestination processing circuitry starts performing the transferredprocessing workload. As mentioned above, the destination processing willnot typically be able to update the values in the source cache.Therefore, after the destination processing circuitry has performedprocessing for a certain number of processing cycles, the data used bythe data processing circuitry (e.g. data stored in memory or adestination cache) is unlikely to be the same as the data still storedin the source cache. This means that the number of processing cyclesthat have elapsed since the start of the performance of the processingworkload by the destination processing circuitry can be an indicatorthat the source cache is no longer useful to the destination processingcircuitry and can be powered down.

Where the apparatus comprises a shared memory shared between the firstand second processing circuitry, the at least one snoop stop event mayinclude an event that occurs when a particular memory region of theshared memory is accessed for the first time by the destinationprocessing circuitry after starting performance of the transferredprocessing workload. The first access to a particular memory region canindicate, for example, that the destination processing circuitry hasstarted a new application associated with the particular memory region,different to the application previously being processed by thedestination processing circuitry. This can indicate that the data in thesource cache, which is not associated with the new application, is nolonger relevant to the destination processing circuitry. Therefore, thefirst access to the particular memory region can trigger the end of thesnooping period.

For similar reasons, the snoop stop event can also include an event thatoccurs when a particular memory region of the shared memory, which wasaccessed by the destination circuitry for an initial period afterstarting performance of the transferred processing workload, is notaccessed by the destination processing circuitry for a predeterminedperiod. When the destination processing circuitry starts processing adifferent application to the one originally processed by the sourceprocessing circuitry, then a memory region associated with the originalapplication may not be accessed for a period of time. This can indicatethat the data in the source cache is no longer being used by thedestination processing circuitry and so can trigger the end of thesnooping period.

Another type of snoop stop event is an event that occurs when thedestination processing circuitry writes to a predetermined memorylocation of the shared memory for the first time after startingperformance of the transferred processing workload. This allows thedestination processing circuitry to signal to the cache snoopingcircuitry that it no longer needs the data in the source cache bywriting to the predetermined memory location.

The set of snoop stop events can include any one or a plurality of theabove mentioned snoop stop events, as well as other types of snoop stopevent.

As used herein, the term “shared memory” refers to memory which can bedirectly accessed by both the first processing circuitry and the secondprocessing circuitry, for example main memory coupled to both the firstand second processing circuitry via an interconnect.

The apparatus may comprise a snoop override controller responsive to asnoop override condition to override snooping of the cache of the sourceprocessing circuitry by the cache snooping circuitry and to control thepower control circuitry to place the source processing circuitry,including the cache, in the power saving state after the transfer of theperformance of the processing workload without waiting for the end ofthe snooping period. In certain situations, snooping of the source cachemay not be useful for the destination processing circuitry. In suchsituations, the snoop override controller can override the cachesnooping circuitry by preventing snooping of the source cache andcontrolling the power control circuitry to place the source processingcircuitry, including the cache, in the power saving state withoutwaiting for the end of the snooping period. The snoop overridecontroller may be provided, for example, as firmware executed on thesource processing circuitry or as part of virtualising software whichmasks the hardware specific information of the processing circuitry fromthe operating system.

For example, it may be known before the transfer of the performance ofthe processing workload that the data in the source cache will not berequired for the processing about to be performed by the destinationprocessing circuitry following the transfer. For example, if the sourceprocessing circuitry has just finished performing a game application,then the data used by the game application may not be useful for thedestination processing circuitry after it begins processing a differentapplication. In this case, the snoop override controller can signal tothe cache snooping circuitry and power control circuitry that thesnooping of the cache is not necessary.

The cache snooping circuitry may comprise a coherent interconnectcoupled to the first and second processing circuitry. The coherentinterconnect has a view of both the source cache and any shared memorypresent in the data processing apparatus. The destination processingcircuitry can simply request data from the coherent interconnect, andthe coherent interconnect can manage whether data is snooped from thesource cache or fetched for memory (depending on whether or not thesnooping period has completed yet and whether or not the data accessrequest results in a hit in the source cache). The coherent interconnectmanages the data accesses so that the destination processing circuitrydoes not need to be aware of the exact location of the requested data.The destination processing circuitry can be unaware of the snooping ofdata from the source cache. The coherent interconnect can in someembodiments also provide a convenient mechanism for transferringarchitectural state data from the source processing circuitry to thedestination processing circuitry during the handover of the processingworkload.

Viewed from another aspect, the present invention provides a dataprocessing apparatus comprising:

first processing means for performing processing and second processingmeans for performing processing, the first processing means and secondprocessing means being configured to perform a processing workload suchthat the processing workload is performed by one of the first processingmeans and the second processing means at a time;

power control means for independently controlling the power supply tothe first processing means and the second processing means;

workload transfer control means for, in response to a transfer stimulus,controlling a transfer of performance of the processing workload from asource processing means to a destination processing means prior to thesource processing means being placed in a power saving condition by thepower control means, the source processing means being one of the firstand second processing means and the destination processing means beingthe other of the first and second processing means; wherein:

at least the source processing means has a cache means for storingcached data values;

the power control means is configured to maintain at least the cachemeans of the source processing means in a powered condition during asnooping period following the start of performance of the transferredprocessing workload by the destination processing means;

the data processing apparatus comprises cache snooping means forsnooping data values in the cache means of the source processing meansduring the snooping period, and retrieving the snooped data values forthe destination processing means; and the power control means isconfigured to place said at least the cache means of the sourceprocessing means in the power saving condition following the end of thesnooping period.

Viewed from yet another aspect, the present invention provides a dataprocessing method for an apparatus comprising first processing circuitryand second processing circuitry configured to perform a processingworkload such that the processing workload is performed by one of thefirst processing circuitry and the second processing circuitry at atime; the method comprising:

performing the processing workload with a source processing circuitry,the source processing circuitry being one of the first and secondprocessing circuitry and comprising a cache, the other of the first andsecond processing circuitry being a destination processing circuitry;

in response to a transfer stimulus, transferring performance of theprocessing workload from the source processing circuitry to thedestination processing circuitry prior to the source processingcircuitry being placed in a power saving condition;

maintaining at least the cache of the source processing circuitry in apowered condition during a snooping period following the start ofperformance of the transferred processing workload by the destinationprocessing circuitry;

during the snooping period, snooping data values in the cache of thesource processing circuitry and retrieving the snooped data values forthe destination processing circuitry; and

placing said at least the cache of the source processing circuitry inthe power saving condition following the end of the snooping period.

Viewed from a further aspect the present invention provides a dataprocessing apparatus comprising:

first processing circuitry and second processing circuitry configured toperform a processing workload such that the processing workload isperformed by one of the first processing circuitry and the secondprocessing circuitry at a time;

a workload transfer controller responsive to a transfer stimulus tocontrol a transfer of performance of the processing workload from asource processing circuitry to a destination processing circuitry priorto the source processing circuitry being placed in a power savingcondition by the power control circuitry, the source processingcircuitry being one of the first and second processing circuitry and thedestination processing circuitry being the other of the first and secondprocessing circuitry; wherein:

at least the destination processing circuitry has a cache;

the destination processing circuitry is configured to invalidate thecache of the destination processing circuitry before the destinationprocessing circuitry starts performing the transferred processingworkload;

the source processing circuitry is configured to continue performing theprocessing workload while the cache of the destination processingcircuitry is being invalidated; and

the workload transfer controller is configured to transfer theperformance of the processing workload to the destination processingcircuitry after the cache of the destination processing circuitry hasbeen invalidated.

The present technique can improve the processing performance by allowingthe source processing circuitry to continue processing the processingworkload for a period following the receipt of the transfer stimuluswhile the cache of a destination processing circuitry is beinginvalidated. By only transferring performance of the processing workloadto the destination processing circuitry after the cache of thedestination processing circuitry has been invalidated, the time duringwhich neither processing circuitry is performing the workload can bereduced. Therefore, the processing workload is performed faster and moreefficiently.

BRIEF DESCRIPTION OF THE DRAWINGS

The present invention will be described further, by way of example only,with reference to embodiments thereof as illustrated in the accompanyingdrawings, in which:

FIG. 1 is a block diagram of a data processing system in accordance withone embodiment;

FIG. 2 schematically illustrates the provision of a switch controller(also referred to herein as a workload transfer controller) inaccordance with one embodiment to logically separate the workload beingperformed by the data processing apparatus from the particular hardwareplatform within the data processing apparatus being used to perform thatworkload;

FIG. 3 is a diagram schematically illustrating the steps performed byboth a source processor and a destination processor in response to aswitching stimulus in order to transfer the workload from the sourceprocessor to the destination processor in accordance with oneembodiment;

FIG. 4A schematically illustrates the storing of the source processingcircuitry's current architectural state into its associated cache duringthe save operation of FIG. 3;

FIG. 4B schematically illustrates the use of the snoop control unit tocontrol the transfer of the source processing circuit's currentarchitectural state to the destination processing circuit during therestore operation of FIG. 3;

FIG. 5 illustrates an alternative structure for providing an acceleratedmechanism for transferring the current architectural state of the sourceprocessing circuitry to the destination processing circuitry during thetransfer operation in accordance with one embodiment;

FIGS. 6A to 6I schematically illustrate the steps performed to transfera workload from a source processing circuit to a destination processingcircuit in accordance with one embodiment;

FIG. 7 is a graph showing energy efficiency variation with performance,and illustrating how the various processor cores illustrated in FIG. 1are used at various points along that curve in accordance with oneembodiment;

FIGS. 8A and 8B schematically illustrate a low performance processorpipeline and a high performance processor pipeline, respectively, asutilised in one embodiment; and

FIG. 9 is a graph showing the variation in power consumed by the dataprocessing system as performance of a processing workload is switchedbetween a low performance, high energy efficiency, processing circuitand a high performance, low energy efficiency, processing circuit.

DESCRIPTION OF EMBODIMENTS

FIG. 1 is a block diagram schematically illustrating a data processingsystem in accordance with one embodiment. As shown in FIG. 1, the systemcontains two architecturally compatible processing circuit instances(the processing circuitry 0 10 and the processing circuitry 1 50), butwith those different processing circuit instances having differentmicro-architectures. In particular, the processing circuitry 10 isarranged to operate with higher performance than the processingcircuitry 50, but with the trade-off that the processing circuitry 10will be less energy efficient than the processing circuitry 50. Examplesof micro-architectural differences will be described in more detailbelow with reference to FIGS. 8A and 8B.

Each processing circuit may include a single processing unit (alsoreferred to herein as a processor core), or alternatively at least oneof the processing circuit instances may itself comprise a cluster ofprocessing units with the same micro-architecture.

In the example illustrated in FIG. 1, the processing circuit 10 includestwo processor cores 15, 20 which are both architecturally andmicro-architecturally identical. In contrast, the processing circuit 50contains only a single processor core 55. In the following description,the processor cores 15, 20 will be referred to as “big” cores, whilstthe processor core 55 will be referred to as a “little” core, since theprocessor cores 15, 20 will typically be more complex than the processorcore 55 due to those cores being designed with performance in mind,whereas in contrast the processor core 55 is typically significantlyless complex due to being designed with energy efficiency in mind.

In FIG. 1, each of the cores 15, 20, 55 is assumed to have its ownassociated local level 1 cache 25, 30, 60, respectively, which may bearranged as a unified cache for storing both instructions and data forreference by the associated core, or can be arranged with a Harvardarchitecture, providing distinct level 1 data and level 1 instructioncaches. Whilst each of the cores is shown as having its own associatedlevel 1 cache, this is not a requirement, and in alternativeembodiments, one or more of the cores may have no local cache.

In the embodiment shown in FIG. 1, the processing circuitry 10 alsoincludes a level 2 cache 35 shared between the core 15 and the core 20,with a snoop control unit 40 being used to ensure cache coherencybetween the two level 1 caches 25, 30 and the level 2 cache 35. In oneembodiment, the level 2 cache is arranged as an inclusive cache, andhence any data stored in either of the level 1 caches 25, 30 will alsoreside in the level 2 cache 35. As will be well understood by thoseskilled in the art, the purpose of the snoop control unit 40 is toensure cache coherency between the various caches, so that it can beensured that either core 15, 20 will always access the most up-to-dateversion of any data when it issues an access request. Hence, purely byway of example, if the core 15 issues an access request for data thatdoes not reside in the associated level 1 cache 25, then the snoopcontrol unit 40 intercepts the request as propagated on from the level 1cache 25, and determines with reference to the level 1 cache 30 and/orthe level 2 cache 35 whether that access request can be serviced fromthe contents of one of those other caches. Only if the data is notpresent in any of the caches is the access request then propagated onvia the interconnect 70 to main memory 80, the main memory 80 beingmemory that is shared between both the processing circuitry 10 and theprocessing circuitry 50.

The snoop control unit 75 provided within the interconnect 70 operatesin a similar manner to the snoop control unit 40, but in this instanceseeks to maintain coherency between the cache structure provided withinthe processing circuitry 10 and the cache structure provided within theprocessing circuitry 50. In examples where the level 2 cache 35 is aninclusive cache, then the snoop control unit maintains hardware cachecoherency between the level 2 cache 35 of the processing circuitry 10and the level 1 cache 60 of the processing circuitry 50. However, if thelevel 2 cache 35 is arranged as an exclusive level 2 cache, then thesnoop control unit 75 will also snoop the data held in the level 1caches 25, 30 in order to ensure cache coherency between the caches ofthe processing circuitry 10 and the cache 60 of the processing circuitry50.

In accordance with one embodiment, only one of the processing circuitry10 and the processing circuitry 50 will be actively processing aworkload at any point in time. For the purposes of the presentapplication, the workload can be considered to comprise at least oneapplication and at least one operating system for running that at leastone application, such as illustrated schematically by the referencenumeral 100 in FIG. 2. In this example, two applications 105, 110 arerunning under control of the operating system 115, and collectively theapplications 105, 110 and the operating system 115 form the workload100. The applications can be considered to exist at a user level, whilstthe operating system exists at a privileged level, and collectively theworkload formed by the applications and the operating system runs on ahardware platform 125 (representing the hardware level view). At anypoint in time that hardware platform will either be provided by theprocessing circuitry 10 or by the processing circuitry 50.

As shown in FIG. 1, power control circuitry 65 is provided forselectively and independently providing power to the processingcircuitry 10 and the processing circuitry 50. Prior to a transfer of theworkload from one processing circuit to the other, only one of theprocessing circuits will typically be fully powered, i.e. the processingcircuit currently performing the workload (the source processingcircuitry), and the other processing circuit (the destination processingcircuitry) will typically be in a power saving condition. When it isdetermined that the workload should be transferred from one processingcircuit to the other, there will then be a period of time during thetransfer operation where both processing circuits are in the powered onstate, but at some point following the transfer operation, the sourceprocessing circuit from which the workload has been transferred willthen be placed into the power saving condition.

The power saving condition can take a variety of forms, dependent onimplementation, and hence for example may be one of a powered offcondition, a partial/full data retention condition, a dormant conditionor an idle condition. Such conditions will be well understood by aperson skilled in the art, and accordingly will not be discussed in moredetail herein.

The aim of the described embodiments is to perform switching of theworkload between the processing circuits depending on the requiredperformance/energy level of the workload. Accordingly, when the workloadinvolves the execution of one or more performance intensive tasks, suchas execution of games applications, then the workload can be executed onthe high performance processing circuit 10, either using one or both ofthe big cores 15, 20. However, in contrast, when the workload is onlyperforming low performance intensity tasks, such as MP3 playback, thenthe entire workload can be transferred to the processing circuit 50, soas benefit from the energy efficiencies that can be realised fromutilising the processing circuit 50.

To make best use of such switching capabilities, it is necessary toprovide a mechanism that allows the switching to take place in a simpleand efficient manner, so that the action of transferring the workloaddoes not consume energy to an extent that will negate the benefits ofswitching, and also to ensure that the switching process is quick enoughthat it does not in itself degrade performance to any significantextent.

In one embodiment, such benefits are at least in part achieved byarranging the processing circuitry 10 to be architecturally compatiblewith the processing circuitry 50. This ensures that the workload can bemigrated from one processing circuitry to the other whilst ensuringcorrect operation. As a bare minimum, such architectural compatibilityrequires both processing circuits 10 and 50 to share the sameinstruction set architecture. However, in one embodiment, sucharchitectural compatibility also entails a higher compatibilityrequirement so as to ensure that the two processing circuit instancesare seen as identical from a programmer's view. In one embodiment, thisinvolves use of the same architectural registers, and one or morespecial purpose registers storing data used by the operating system whenexecuting applications. With such a level of architecturalcompatibility, it is then possible to mask from the operating system 115the transfer of the workload between processing circuits, so that theoperating system is entirely unaware as to whether the workload is beingexecuted on the processing circuitry 10 or on the processing circuitry50.

In one embodiment, the handling of the transfer from one processingcircuit to the other is managed by the switch controller 120 shown inFIG. 2 (also referred to therein as a virtualiser and elsewhere hereinas a workload transfer controller). The switch controller can beembodied by a mixture of hardware, firmware and/or software features,but in one embodiment includes software similar in nature to hypervisorsoftware found in virtual machines to enable applications written in onenative instruction set to be executed on a hardware platform adopting adifferent native instruction set. Due to the architectural compatibilitybetween the two processing circuits 10, 50, the switch controller 120can mask the transfer from the operating system 115 merely by maskingone or more items of predetermined processor specific configurationinformation from the operating system. For example, the processorspecific configuration information may include the contents of a CP15processor ID register and CP15 cache type register.

In such an embodiment, the switch controller then merely needs to ensurethat any current architectural state held by the source processingcircuit at the time of the transfer, and that is not at the time thetransfer is initiated already available from shared memory 80, is madeavailable to the destination processing circuit in order to enable thedestination circuit to be in a position to successfully take overperformance of the workload. Using the earlier described example, sucharchitectural state will typically comprise the current values stored inthe architectural register file of the source processing circuitry,along with the current values of one or more special purpose registersof the source processing circuitry. Due to the architecturalcompatibility between the processing circuits 10, 50, if this currentarchitectural state can be transferred from the source processingcircuit to the destination processing circuit, the destinationprocessing circuit will then be in a position to successfully take overperformance of the workload from the source processing circuit.

Whilst architectural compatibility between the processing circuits 10,50 facilitates transfer of the entire workload between the twoprocessing circuits, in one embodiment the processing circuits 10, 50are micro-architecturally different from each other, such that there aredifferent performance characteristics, and hence energy consumptioncharacteristics, associated with the two processing circuits. Asdiscussed earlier, in one embodiment, the processing circuit 10 is ahigh performance, high energy consumption, processing circuit, while theprocessing circuit 50 is a lower performance, lower energy consumption,processing circuit. The two processing circuits can bemicro-architecturally different from each other in a number of respects,but typically will have at least one of different execution pipelinelengths, and/or different execution resources. Differences in pipelinelength will typically result in differences in operating frequency,which in turn will have an effect on performance. Similarly, differencesin execution resources will have an effect on throughput and henceperformance. Hence, by way of example, the processing circuitry 10 mayhave wider execution resources and/or more execution resources, in orderto improve throughput. Further, the pipelines within the processor cores15, 20 may be arranged to perform out-of-order superscalar processing,whilst the simpler core 55 within the energy efficient processingcircuit 50 may be arranged as an in-order pipeline. A further discussionof micro-architectural differences will be provided later with referenceto FIGS. 8A and 8B.

The generation of a transfer stimulus to cause the switch controller 120to instigate a handover operation to transfer the workload from oneprocessing circuit to another can be triggered for a variety of reasons.For example, in one embodiment, applications may be profiled and markedas ‘big’, ‘little’ or ‘big/little’, whereby the operating system caninterface with the switch controller to move the workload accordingly.Hence, by such an approach, the generation of the transfer stimulus canbe mapped to particular combinations of applications being executed, toensure that when high performance is required, the workload is executedon the high performance processing circuit 10, whereas when thatperformance is not required, the energy efficient processing circuit 50is instead used. In other embodiments, algorithms could be executed todynamically determine when to trigger a transfer of the workload fromone processing circuit to the other based on one or more inputs. Forexample, the performance counters of the processing circuitry can be setup to count performance sensitive events (for example the number ofinstructions executed, or the number of load-store operations). Coupledwith a cycle counter or a system timer, this allows identification thata highly compute intensive application is executing that may be betterserved by switching to the higher performance processing circuitry, oridentification of a large number of load-store operations indicating anIO intensive application which may be better served on the energyefficient processing circuitry, etc.

As a yet further example of when a transfer stimulus might be generated,the data processing system may include one or more thermal sensors 90for monitoring the temperature of the data processing system duringoperation. It can be the case that modern high performance processingcircuits, for example those running at GHz frequencies, sometimes reach,or exceed, the thermal limits that they were designed to operate within.By using such thermal sensors 90, it can be detected when such thermallimits are being reached, and under those conditions a transfer stimuluscan be generated to trigger a transfer of the workload to a more energyefficient processing circuit in order to bring about an overall coolingof the data processing system. Hence, considering the example of FIG. 1where the processing circuit 10 is a high performance processing circuitand the processing circuit 50 is a lower performance processing circuitconsuming less energy, migration of the workload from the processingcircuit 10 to the processing circuit 50 when the thermal limits of thedevice are being reached will bring about a subsequent cooling of thedevice, whilst still allowing continued program execution to take place,albeit at lower throughput.

Whilst in FIG. 1 two processing circuits 10, 50 are shown, it will beappreciated that the techniques of the above described embodiments canalso be applied to systems incorporating more than two differentprocessing circuits, allowing the data processing system to span alarger range of performance/energy levels. In such embodiments, each ofthe different processing circuits will be arranged to be architecturallycompatible with each other to allow the ready migration of the entireworkload between the processing circuits, but will also bemicro-architecturally different to each other to allow choices to bemade between the use of those processing circuits dependent on requiredperformance/energy levels.

FIG. 3 is a flow diagram illustrating the sequence of steps performed onboth the source processor and the destination processor when theworkload is transferred from the source processor to the destinationprocessor upon receipt of a transfer stimulus. Such a transfer stimulusmay be generated by the operating system 115 or the virtualiser 120 viaa system firmware interface resulting in the detection of the switchingstimulus at step 200 by the source processor (which will be running notonly the workload, but also the virtualiser software forming at leastpart of the switch controller 120). Receipt of the transfer stimulus(also referred to herein as the switching stimulus) at step 200 willcause the power controller 65 to initiate a power on and reset operation205 on the destination processor. Following such power on and reset, thedestination processor will invalidate its local cache at step 210, andthen enable snooping at step 215. At this point, the destinationprocessor will then signal to the source processor that it is ready forthe transfer of the workload to take place, this signal causing thesource processor to execute a save state operation at step 225. Thissave state operation will be discussed in more detail later withreference to FIG. 4A, but in one embodiment involves the sourceprocessing circuitry storing to its local cache any of its currentarchitectural state which is not available from shared memory at thetime the handover operation is initiated, and that is necessary for thedestination processor to successfully take over performance of theworkload.

Following the save state operation 225, a switch state signal will beissued to the destination processor 230 indicating to the destinationprocessor that it should now begin snooping the source processor inorder to retrieve the required architectural state. This process takesplace via a restore state operation 230 which will be discussed in moredetail later with reference to FIG. 4B, but which in one embodimentinvolves the destination processing circuitry initiating a sequence ofaccesses which are intercepted by the snoop control unit 75 within theinterconnect 70, and which cause the cached copy of the architecturalstate in the source processor's local cache to be retrieved and returnedto the destination processor.

Following step 230, the destination processor is then in a position totake over processing of the workload, and accordingly normal operationbegins at step 235.

In one embodiment, once normal operation begins on the destinationprocessor, the source processor's cache could be cleaned as indicated atstep 250, in order to flush any dirty data to the shared memory 80, andthen the source processor could be powered down at step 255. However, inone embodiment, to further improve the efficiency of the destinationprocessor, the source processor is arranged to remain powered up for aperiod of time referred to in FIG. 3 as the snooping period. During thistime, at least one of the caches of the source circuit remains poweredup, so that its contents can be snooped by the snoop control circuit 75in response to access requests issued by the destination processor.Following the transfer of the entire workload using the processdescribed in FIG. 3, it is expected that for at least an initial periodof time after which the destination processor begins operation of theworkload, some of the data required during the performance of theworkload will reside in the source processor's cache. If the sourceprocessor had flushed its contents to memory, and been powered down,then the destination processor would during these early stages operaterelatively inefficiently, since there would be a lot of cache misses inits local cache, and a lot of fetching of data from shared memory,resulting in a significant performance impact whilst the destinationprocessor's cache is “warmed up”, i.e. filled with data values requiredby the destination processor circuit to perform the operations specifiedby the workload. However, by leaving the source processor's cachepowered up during the snooping period, the snoop control circuit 75 willbe able to service a lot of these cache miss requests with reference tothe source circuit's cache, yielding significant performance benefitswhen compared with the retrieval of that data from shared memory 80.

However, this performance benefit is only expected to last for a certainamount of time following the switch, after which the contents of thesource processor's cache will become stale. Accordingly, at some point asnoop stop event will be generated to disable snooping at step 245,whereafter the source processor's cache will be cleaned at step 250, andthen the source processor will be powered down at step 255. A discussionof the various scenarios under which the snoop stop event may begenerated will be discussed in more detail later with reference to FIG.6G.

FIG. 4A schematically illustrates the save operation performed at step225 in FIG. 3 in accordance with one embodiment. In particular, in oneembodiment, the architectural state that needs to be stored from thesource processing circuitry 300 to the local cache 330 consists of thecontents of a register file 310 referenced by an arithmetic logic unit(ALU) 305 during the performance of data processing operations, alongwith the contents of various special purpose registers 320 identifying avariety of pieces of information required by the workload tosuccessfully enable that workload to be taken over by the destinationprocessing circuitry. The contents of the special purpose registers 320will include for example a program counter value identifying a currentinstruction being executed, along with various other information. Forexample, other special purpose registers include processor statusregisters (e.g. the CPSR and SPSR in the ARM architecture) that holdcontrol bits for processor mode, interrupt masking, execution state andflags. Other special purpose registers include architectural control(the CP15 system control register in the ARM architecture) that holdbits to alter data endianness, turn the MMU on or off, turndata/instruction caches on or off, etc. Other special purpose registersin CP15 store exception address and status information.

As schematically illustrated in FIG. 4A, the source processing circuit300 will also typically hold some processor specific configurationinformation 315, but this information does not need saving to the cache330, since it will not be applicable to the destination processingcircuitry. The processor specific configuration information 315 istypically hard-coded in the source processing circuit 300 using logicconstants, and may include, for example, the contents of the CP15processor ID register (which will be different for each processingcircuit) or the contents of the CP15 cache type register (which willdepend on the configuration of the caches 25, 30, 60, for exampleindicating that the caches have different line lengths). When theoperating system 115 requires a piece of processor specificconfiguration information 315, then unless the processor is already inhypervisor mode, an execution trap to hypervisor mode occurs. Inresponse, the virtualiser 120 may in one embodiment indicate the valueof the information requested, but in another embodiment will return a“virtual” value. In the case of the processor ID value, this virtualvalue can be chosen to be the same for both “big” and “little”processors, thereby causing the actual hardware configuration to behidden from the operating system 115 by the virtualiser 120.

As illustrated schematically in FIG. 4A, during the save operation, thecontents of the register file 310 and of the special purpose registers320 is stored by the source processing circuitry into the cache 330 toform a cached copy 335. This cached copy is then marked as shareable,which allows the destination processor to snoop this state via the snoopcontrol unit 75.

The restore operation subsequently performed on the destinationprocessor is then illustrated schematically in FIG. 4B. In particular,the destination processing circuitry 350, which may or may not have itsown local cache) will issue a request for a particular item ofarchitectural state, with that request being intercepted by the snoopcontrol unit 75. The snoop control unit will then issue a snoop requestto the source processing circuit's local cache 330 to determine whetherthat item of architectural state is present in the source's cache.Because of the steps taken during the save operation discussed in FIG.4A, a hit will be detected in the source's cache 330, resulting in thatcached architectural state being returned via the snoop control unit 75to the destination processing circuit 350. This process can be repeatediteratively until all of the items of architectural state have beenretrieved via snooping of the source processing circuit's cache. Anyprocessor specific configuration information relevant to destinationprocessing circuit 350 is typically hard-coded in the destinationprocessing circuit 350 as discussed earlier. Thus, once the restoreoperation has been completed, the destination processing circuitry thenhas all the information required to enable it to successfully take overhandling of the workload.

Further, in one embodiment, regardless of whether the workload 100 isbeing performed by the “big” processing circuit 10 or “little”processing circuit 50, the virtualiser 120 provides the operating system115 with virtual configuration information having the same values, andso the hardware differences between the “big” and “little” processingcircuits 10, 50 are masked from the operating system 115 by thevirtualiser 120. This means that the operating system 115 is unawarethat the performance of the workload 100 has been transferred to adifferent hardware platform.

In accordance with the save and restore operations described withreference to FIGS. 4A and 4B, the various processor instances 10, 50 arearranged to be hardware cache coherent with one another in order toreduce the amount of time, energy and hardware complexity involved intransferring the architectural state from the source processor to thedestination processor. The technique uses the source processor's localcache to store all of the state that must be transferred from the sourceprocessor to the destination processor and which is not available fromshared memory at the time the transfer operation takes place. Becausethe state is marked as shareable within the source processor's cache,this allows the hardware cache coherent destination processor to snoopthis state during the transfer operation. By using such a technique, itis possible to transfer the state between the processor instanceswithout the need to save that state either to main memory or to a localmemory mapped storage element. This hence yields significant performanceand energy consumption benefits, increasing the variety of situations inwhich it would be appropriate to switch the workload in order to seek torealise energy consumption benefits.

However, whilst the technique of using cache coherence as describedabove provides one accelerated mechanism for making the currentarchitectural state available to the destination processor withoutrouting of the current architectural state via the shared memory, it isnot the only way in which such an accelerated mechanism could beimplemented. For example, FIG. 5 illustrates an alternative mechanismwhere a dedicated bus 380 is provided between the source processingcircuitry 300 and the destination processing circuitry 350 in order toallow the architectural state to be transferred during the handoveroperation. Hence, in such embodiments, the save and restore operations225, 230 of FIG. 3 are replaced with an alternative transfer mechanismutilising the dedicated bus 380. Whilst such an approach will typicallyhave a higher hardware cost than employing the cache coherency approach(the cache coherency approach typically making use of hardware alreadyin place within the data processing system), it would provide an evenfaster way of performing the switching, which could be beneficial incertain implementations.

FIGS. 6A to 6I schematically illustrate a series of steps that areperformed in order to transfer performance of a workload from the sourceprocessing circuitry 300 to the destination processing circuitry 350.The source processing circuitry 300 is whichever of the processingcircuits 10, 50 is performing the workload before the transfer, with thedestination processing circuitry being the other of the processingcircuits 10, 50.

FIG. 6A shows the system in an initial state in which the sourceprocessing circuitry 300 is powered by the power controller 65 and isperforming the processing workload 100, while the destination processingcircuitry 350 is in the power saving condition. In this embodiment, thepower saving condition is a power off condition, but as mentioned aboveother types of power saving condition may also be used. The workload100, including applications 105, 110 and an operating system 115 forrunning the applications 105, 110, is abstracted from the hardwareplatform of the source processing circuitry 300 by the virtualiser 120.While performing the workload 100, the source processing circuitry 300maintains architectural state 400, which may comprise for example thecontents of the register file 310 and special purpose registers 320 asshown in FIG. 4A.

In FIG. 6B, a transfer stimulus 430 is detected by the virtualiser 120.While the transfer stimulus 430 is shown in FIG. 6B as an external event(e.g. detection of thermal runaway by the thermal sensor 90), thetransfer stimulus 430 could also be an event triggered by thevirtualiser 120 itself or by the operating system 115 (e.g. theoperating system 115 could be configured to inform the virtualiser 120when a particular type of application is to be processed). Thevirtualiser 120 responds to the transfer stimulus 430 by controlling thepower controller 65 to supply power to the destination processingcircuitry 350, in order to place the destination processing circuitry350 in a powered state.

In FIG. 6C, the destination processing circuitry 350 starts executingthe virtualiser 120. The virtualiser 120 controls the destinationprocessing circuitry 350 to invalidate its cache 420, in order toprevent processing errors caused by erroneous data values which may bepresent in the cache 420 on powering up the destination processingcircuitry 350. While the destination cache 420 is being invalidated, thesource processing circuitry 350 continues to perform the workload 100.When invalidation of the destination cache 420 is complete, thevirtualiser 120 controls the destination processing circuitry 350 tosignal to the source processing circuitry 300 that it is ready for thehandover of the workload 100. By continuing processing of the workload100 on the source processing circuitry 300 until the destinationprocessing circuitry 350 is ready for the handover operation, theperformance impact of the handover can be reduced.

At the next stage, shown in FIG. 6D, the source processing circuitry 300stops performing the workload 100. During this stage, neither the sourceprocessing circuitry 300 nor the destination processing circuitry 350performs the workload 100. A copy of the architectural state 400 istransferred from the source processing circuitry 300 to the destinationprocessing circuitry 350. For example, the architectural state 400 canbe saved to the source cache 410 and restored to the destinationprocessing circuitry 350 as shown in FIGS. 4A and 4B, or can betransferred over a dedicated bus as shown in FIG. 5. The architecturalstate 400 contains all the state information required for thedestination processing circuitry 350 to perform the workload 100, otherthan the information already present in the shared memory 80.

Having transferred the architectural state 400 to the destinationprocessing circuitry 350, the source processing circuitry 300 is placedin the power saving state by the power control circuitry 65 (see FIG.6E), with the exception that the source cache 410 remains powered.Meanwhile, the destination processing circuitry 350 begins performingthe workload 100 using the transferred architectural state 400.

When the destination processing circuitry 350 begins processing theworkload 100, the snooping period begins (see FIG. 6F). During thesnooping period, the snoop control unit 75 can snoop the data stored inthe source cache 410 and retrieve the data on behalf of the destinationprocessing circuitry 350. When the destination processing circuitry 350requests data that is not present in the destination cache 420, thedestination processing circuitry 350 requests data from the snoopcontrol unit 75. The snoop control unit 75 then snoops the source cache410, and if the snoop results in a cache hit then the snoop control unit75 retrieves the snooped data from the source cache 410 and returns itto the destination processing circuitry 350 where the snooped data canbe stored in the destination cache 420. On the other hand, if the snoopresults in a cache miss in the source cache 410 then the requested datais fetched from the shared memory 80 and returned to the destinationprocessing circuitry 350. Since accesses to data in the source cache 410are faster and require less energy than accesses to shared memory 80,snooping the source cache 410 for a period improves processingperformance and reduces energy consumption during an initial periodfollowing the handover of the workload 100 to the destination processingcircuitry 350.

At the step shown in FIG. 6G, the snoop control unit 75 detects a snoopstop event which indicates that it is no longer efficient to maintainthe source cache 410 in the powered state. The snoop stop event triggersthe end of the snooping period. The snoop stop event may be any one of aset of snoop stop events monitored by the snoop control circuitry 75.For example, the set of snoop stop events can include any one or more ofthe following events:

-   -   a) when the percentage or fraction of snoop hits that result in        a cache hit in the source cache 410 (i.e. a quantity        proportional to number of snoop hits/number of total snoops)        drops below a predetermined threshold level after the        destination processing circuitry 350 has started performing the        workload 100;    -   b) when the number of transactions, or the number of        transactions of a predetermined type (e.g. cacheable        transactions), performed since the destination processing        circuitry 350 began performing the workload 100 exceeds a        predetermined threshold;    -   c) when the number of processing cycles elapsed since the        destination processing circuitry 350 began performing the        workload 100 exceeds a predetermined threshold;    -   d) when a particular region of the shared memory 80 is accessed        for the first time since the destination processing circuitry        350 began performing the workload 100;    -   e) when a particular region of the shared memory 80, which was        accessed for an initial period after the destination processing        circuitry 350 began performing the workload 100, is not accessed        for a predetermined number of cycles or a predetermined period        of time;    -   f) when the destination processing circuitry 350 writes to a        predetermined memory location for the first time since starting        to perform the transferred workload 100.        These snoop stop events can be detected using programmable        counters in the coherent interconnect 70 that includes the snoop        control unit 75. Other types of snoop stop event may also be        included in the set of snoop stop events.

On detecting a snoop stop event, the snoop control unit 75 sends a snoopstop signal 440 to the source processor 300. The snoop control unit 75stops snooping the source cache 410 and from now on responds to dataaccess requests from the destination processing circuitry 350 byfetching the requested data from shared memory 80 and returning thefetched data to the destination processing circuitry 350, where thefetched data can be cached.

In FIG. 6H, the source cache's control circuit is responsive to thesnoop stop signal 440 to clean the cache 410 in order to save to theshared memory 80 any valid and dirty data values (i.e. whose cachedvalue is more up-to-date than the corresponding value in shared memory80).

In FIG. 6I, the source cache 410 is then powered down by the powercontroller 65 so that the source processing circuitry 300 is entirely inthe power saving state. The destination processing circuitry 350continues to perform the workload 100. From the point of view of theoperating system 115, the situation is now the same as in FIG. 6A. Theoperating system 115 is not aware that execution of the workload hastransferred from one processing circuit to another processing circuit.When another transfer stimulus occurs, then the same steps of FIGS. 6Ato 6I can be used to switch performance of the workload back to thefirst processor (in this case which of the processing circuits 10, 50are the “source processing circuitry” and “destination processingcircuitry” will be reversed).

In the embodiment of FIGS. 6A to 6I, independent power control to thecache 410 and the source processing circuitry 300 is available so thatthe source processing circuitry 300, other than the source cache 410,can be powered down once the destination processing circuitry 350 hasstarted performing the workload (see FIG. 6E), while only the cache 410of the source processing circuitry 350 remains in the powered state (seeFIGS. 6F to 6H). The source cache 410 is then powered down in FIG. 6I.This approach can be useful to save energy, especially when the sourceprocessing circuitry 300 is the “big” processing circuit 10.

However, it is also possible to continue to power the entire sourceprocessing circuitry 300 during the snooping period, and to then placethe source processing circuitry 300 as a whole in the power saving stateat FIG. 6I, following the end of the snooping period and the cleaning ofthe source cache 410. This may be more useful in the case where thesource cache 410 is too deeply embedded with the source processor coreto be able to be powered independently from the source processor core.This approach can also be more practical when the source processor isthe “little” processing circuit 50, whose power consumption isinsignificant in comparison to the “big” processing circuit 10, sinceonce the “big” processing circuit 10 has started processing thetransferred workload 100 then switching the “little” processing circuit50, other than the cache 60, to the power saving state during thesnooping period may have little effect on the overall power consumptionof the system. This may mean that the extra hardware complexity ofproviding individual power control to the “little” processing circuit 50and the “little” core's cache 60 may not be justified.

In some situations, it may be known before the workload transfer thatthe data stored in the source cache 410 will not be needed by thedestination processing circuitry 350 when it begins to perform theworkload 100. For example, the source processing circuitry 300 may justhave completed an application when the transfer occurs, and thereforethe data in the source cache 410 at the time of the transfer relates tothe completed application and not the application to be performed by thedestination processing circuitry 350 after the transfer. In such a case,a snoop override controller can trigger the virtualiser 120 and snoopcontrol circuitry 75 to override the snooping of the source cache 410and to control the source processing circuit 300 to clean and power downthe source cache 410 without waiting for a snoop stop event to signalthe end of the snooping period. In this case, the technique of FIGS. 6Ato 6I would jump from the step of FIG. 6E straight to the step of FIG.6G, without the step of FIG. 6F in which data is snooped from the sourcecache 410. Thus, if it is known in advance that the data in the sourcecache 410 will not be useful for the destination processing circuitry350, power can be saved by placing the source cache 410 and sourceprocessing circuitry 300 in the power saving condition without waitingfor a snoop stop event. The snoop override controller can be part of thevirtualiser 120, or can be implemented as firmware executing on thesource processing circuitry 300. The snoop override controller couldalso be implemented as a combination of elements, for example theoperating system 115 could inform the virtualiser 120 when anapplication has finished, and the virtualiser 120 could then overridesnooping of the source cache 410 if a transfer occurs when anapplication has finished.

FIG. 7 is a graph on which the line 600 illustrates how energyconsumption varies with performance. For various portions of this graph,the data processing system can be arranged to utilise differentcombinations of the processor cores 15, 20, 55 illustrated in FIG. 1 inorder to seek to obtain the appropriate trade-off between performanceand energy consumption. Hence, by way of example, when a number of veryhigh performance tasks need to be executed, it is possible to run bothof the big cores 15, 20 of the processing circuit 10 in order to achievethe desired performance. Optionally supply voltage variation techniquescan be used to allow some variation in performance and energyconsumption when utilising these two cores.

When the performance requirements drop to a level where the requiredperformance can be achieved using only one of the big cores, then thetasks can be migrated on to just one of the big cores 15, 20, with theother core being powered down or put into some other power savingcondition. Again supply voltage variation can be used to allow somevariation between performance and energy consumption when using such asingle big core. It should be noted that the transition from two bigcores to one big core will not require a generation of a transferstimulus, nor the use of the above described techniques for transferringworkload, since in all instances it is the processing circuit 10 that isbeing utilised, and the processing circuit 50 will be in a power savingcondition. However, as indicated by the dotted line 610 in FIG. 7, whenthe performance drops to a level where the small core is able to achievethe required performance, then a transfer stimulus can be generated totrigger the earlier described mechanism for transferring the entireworkload from the processing circuit 10 to the processing circuit 50,such that the entire workload is then run on the small core 55, with theprocessing circuit 10 being placed into a power saving condition. Again,supply voltage variation can be used to allow some variation in theperformance and energy consumption of the small core 55.

FIGS. 8A and 8B respectively illustrate micro-architectural differencesbetween a low performance processor pipeline 800 and a high performanceprocessor pipeline 850 according to one embodiment. The low performanceprocessor pipeline 800 of FIG. 8A would be suitable for the littleprocessing core 55 of FIG. 1, whereas the high performance processorpipeline 850 of FIG. 8B would be suitable for the big cores 15, 20.

The low performance processor pipeline 800 of FIG. 8A comprises a fetchstage 810 for fetching instructions from memory 80, a decode stage 820for decoding the fetched instructions, an issue stage 830 for issuinginstructions for execution, and multiple execution pipelines includingan integer pipeline 840 for performing integer operations, a MACpipeline 842 for performing multiply accumulate operations, and aSIMD/FPU pipeline 844 for performing SIMD (single instruction, multipledata) operations or floating point operations. In the low performanceprocessor pipeline 800, the issue stage 830 issues a single instructionat a time, and issues the instructions in the order in which theinstructions are fetched.

The high performance processor pipeline 850 of FIG. 8B comprises a fetchstage 860 for fetching instructions from memory 80, a decode stage 870for decoding the fetched instructions, a rename stage 875 for renamingregisters specified in the decoded instructions, a dispatch stage 880for dispatching instructions for execution, and multiple executionpipelines including two integer pipelines 890, 892, a MAC pipeline 894,and two SIMD/FPU pipelines 896, 898. In the high performance processorpipeline 850, the dispatch stage 880 is a parallel issue stage which canissue multiple instructions to different ones of the pipelines 890, 892,894, 896, 898 at once. The dispatch stage 880 can also issue theinstructions out-of-order. Unlike in the low performance processorpipeline 800, the SIMD/FPU pipelines 896, 898 are variable length, whichmeans that operations proceeding through the SIMD/FPU pipelines 896, 898can be controlled to skip certain stages. An advantage of such anapproach is that if multiple execution pipelines each have differentresources, there is no need to artificially lengthen the shortestpipeline to make it the same length as the longest pipeline, but insteadlogic is required to deal with the out-of-order nature of the resultsproduced by the different pipelines (for example to place everythingback in order if a processing exception occurs).

The rename stage 875 is provided to map register specifiers, which areincluded in program instructions and identify particular architecturalregisters when viewed from a programmer's model point of view, tophysical registers which are the actual registers of the hardwareplatform. The rename stage 875 enables a larger pool of physicalregisters to be provided by the microprocessor than are present withinthe programmer's model view of the microprocessor. This larger pool ofphysical registers is useful during out-of-order execution because itenables hazards such as write-after-write (WAW) hazards to be avoided bymapping the same architectural register specified in two or moredifferent instructions to two or more different physical registers, sothat the different instructions can be executed concurrently. For moredetails of register renaming techniques, the reader is referred tocommonly owned US patent application US 2008/114966 and U.S. Pat. No.7,590,826.

The low-performance pipeline 800 and high-performance pipeline 850 aremicro-architecturally different in a number of ways. Themicro-architectural differences can include:

-   -   a) the pipelines having different stages. For example, the        high-performance pipeline 850 has a rename stage 875 which is        not present in the low-performance pipeline 800.    -   b) the pipeline stages having different capabilities. For        example, the issue stage 830 of the low-performance pipeline 800        is capable only of single issue of instructions, whereas the        dispatch stage 880 of the high performance pipeline 850 can        issue instructions in parallel. Parallel issue improves the        processing throughput of the pipeline and so improves        performance.    -   c) the pipeline stages having different lengths. For example,        the decode stage 870 of the high-performance pipeline 850 may        include three sub-stages whereas the decode stage 820 of the        low-performance pipeline 800 may include only a single        sub-stage. The longer a pipeline stage (the greater the number        of sub-stages), the greater the number of instructions which can        be in flight at the same time, and so greater the operating        frequency at which the pipeline can operate, which results in a        higher level of performance.    -   d) a different number of execution pipelines (e.g. the        high-performance pipeline 850 has more execution pipelines than        the low-performance pipeline 800). By providing more execution        pipelines, more instructions can be processed in parallel and so        performance is increased.    -   e) providing in-order execution (as in pipeline 800) or        out-of-order execution (as in pipeline 850). When instructions        can be executed out-of-order, then performance is improved since        the execution of instructions can be dynamically scheduled to        optimize performance. For example, in the low-performance        in-order pipeline 800 a series of MAC instructions would need to        be executed one by one by the MAC pipeline 842 before a later        instruction could be executed by one of the integer pipeline 840        and SIMD/floating point pipeline 844. In contrast, in the        high-performance pipeline 850 then the MAC instructions could be        executed by the MAC pipe 894, while (subject to any data hazards        which cannot be resolved by renaming) a later instruction using        a different execution pipeline 890, 892, 896, 898 can be        executed in parallel with the MAC instructions. This means that        out-of-order execution can improve processing performance.        These, and other examples of, micro-architectural differences        result in the pipeline 850 providing higher performance        processing than the pipeline 800. On the other hand, the        micro-architectural differences also make the pipeline 850        consume more energy than the pipeline 800. Thus, providing        micro-architecturally different pipelines 800, 850 enables the        processing of the workload to be optimised for either high        performance (by using a “big” processing circuit 10 having the        high-performance pipeline 850) or energy efficiency (by using a        “little” processing circuit 50 having the low-performance        pipeline 800).

FIG. 9 shows a graph illustrating the variation in power consumption ofthe data processing system as performance of the workload 100 isswitched between the big processing circuit 10 and the little processingcircuit 50.

At point A of FIG. 9, the workload 100 is being performed on the littleprocessing circuitry 50 and so power consumption is low. At point B, atransfer stimulus occurs indicating that high-intensity processing is tobe performed and so the performance of the workload is handed over tothe big processing circuitry 10. The power consumption then rises andremains high at point C while the big processing circuitry 10 isperforming the workload. At point D it is assumed that both big coresare operating in combination to process the workload. If however theperformance requirements drop to a level where the workload can behandled by only one of the big cores, then the workload is migrated toonly one of the big cores, and the other is powered down, as indicatedby the drop in power to the level adjacent point E. However, at point E,another transfer stimulus occurs (indicating that a return tolow-intensity processing is desired) to trigger a transfer of theperformance of the workload back to the little processing circuitry 50.

When the little processing circuitry 50 starts processing the processingworkload, most of the big processing circuitry is in the power savingstate, but the cache of the big processing circuitry 10 remains poweredduring the snooping period (point F in FIG. 9) to enable the data in thecache to be retrieved for the little processing circuitry 50. Hence, thecache of the big processing circuitry 10 causes the power consumption atpoint F to be higher than at point A when only the little processingcircuitry 50 was powered. At the end of the snooping period, the cacheof the big processing circuitry 10 is powered down and at point G powerconsumption returns to the low level when only the little processingcircuitry 50 is active.

As mentioned above, in FIG. 9 the power consumption is higher during thesnooping period at point F than at point G due to the cache of the bigprocessing circuitry 10 being powered during the snooping period.Although this increase in power consumption is indicated only followingthe big-to-little transition, following the little-to-big transitionthere may also be a snooping period, during which the data in the cacheof the little processing circuitry 50 can be snooped on behalf of thebig processing circuitry 10 by the snoop control unit 75. The snoopingperiod for the little-to-big transition has not been indicated in FIG. 9because the power consumed by leaving the cache of the little processingcircuitry 50 in a powered state during the snooping period isinsignificant in comparison with the power consumed by the bigprocessing circuitry 10 when performing the processing workload, and sothe very small increase in power consumption due to the cache of thelittle processing circuitry 50 being powered is not visible in the graphof FIG. 9.

The above described embodiments describe a system containing two or morearchitecturally compatible processor instances with micro-architecturesoptimised for energy efficiency or performance. The architectural staterequired by the operating system and applications can be switchedbetween the processor instances depending on the requiredperformance/energy level, in order to allow the entire workload to beswitched between the processor instances. In one embodiment, only one ofthe processor instances is running the workload at any given time, withthe other processing instance being in a power saving condition, or inthe process of entering/exiting the power saving condition.

In one embodiment, the processor instances may be arranged to behardware cache coherent with one another to reduce the amount of time,energy and hardware complexity involved in switching the architecturalstate from the source processor to the destination processor. Thisreduces the time to perform the switching operation, which increases theopportunities in which the techniques of embodiments can be used.

Such systems may be used in a variety of situations where energyefficiency is important for either battery life and/or thermalmanagement, and the spread of performance is such that a more energyefficient processor can be used for lower processing workloads while ahigher performance processor can be used for higher processingworkloads.

Because the two or more processing instances are architecturallycompatible, from an application perspective the only difference betweenthe two processors is the performance available. Through techniques ofone embodiment, all architectural state required can be moved betweenthe processors without needing to involve the operating system, suchthat it is then transparent to the operating system and the applicationsrunning on the operating system as to which processor that operatingsystem and applications are running on.

When using architecturally compatible processor instances as describedin the above embodiments, the total amount of architectural state thatneeds to be transferred can easily fit within a data cache, and sincemodern processing systems often implement cache coherence, then bystoring the architectural state to be switched inside the data cache,the destination processor can rapidly snoop this state in an energyefficient way making use of existing circuit structures.

In one described embodiment, the switching mechanism is used to ensurethermal limits for the data processing system are not breached. Inparticular, when the thermal limits are about to be reached, the entireworkload can be switched to a more energy efficient processor instance,allowing the overall system to cool while continued program executiontakes place, albeit at a lower throughput.

Although a particular embodiment has been described herein, it will beappreciated that the invention is not limited thereto and that manymodifications and additions thereto may be made within the scope of theinvention. For example, various combinations of the features of thefollowing dependent claims could be made with the features of theindependent claims without departing from the scope of the presentinvention.

1. A data processing apparatus comprising: first processing circuitryand second processing circuitry configured to perform a processingworkload such that the processing workload is performed by one of thefirst processing circuitry and the second processing circuitry at atime; power control circuitry for independently controlling the powersupply to the first processing circuitry and the second processingcircuitry; a workload transfer controller responsive to a transferstimulus to control a transfer of performance of the processing workloadfrom a source processing circuitry to a destination processing circuitryprior to the source processing circuitry being placed in a power savingcondition by the power control circuitry, the source processingcircuitry being one of the first and second processing circuitry and thedestination processing circuitry being the other of the first and secondprocessing circuitry; wherein: at least the source processing circuitryhas a cache; the power control circuitry is configured to maintain atleast the cache of the source processing circuitry in a poweredcondition during a snooping period following the start of performance ofthe transferred processing workload by the destination processingcircuitry; the data processing apparatus comprises cache snoopingcircuitry configured during the snooping period to snoop data values inthe cache of the source processing circuitry and to retrieve the snoopeddata values for the destination processing circuitry; and the powercontrol circuitry is configured to place said at least the cache of thesource processing circuitry in the power saving condition following theend of the snooping period.
 2. The data processing apparatus accordingto claim 1, wherein the processing workload includes at least oneprocessing application and at least one operating system for running theat least one processing application.
 3. The data processing apparatusaccording to claim 2, wherein the workload transfer controller isconfigured during the transfer to mask predetermined processor specificconfiguration information from said at least one operating system suchthat the transfer of the workload is transparent to said at least oneoperating system.
 4. The data processing apparatus according to claim 3,wherein the workload transfer controller comprises at leastvirtualisation software logically separating the at least one operatingsystem from the first processing circuitry and the second processingcircuitry.
 5. The data processing apparatus according to claim 1,wherein the first processing circuitry is architecturally compatiblewith the second processing circuitry such that a processing workload tobe performed by the data processing apparatus can be performed on eitherthe first processing circuitry or the second processing circuitry. 6.The data processing apparatus according to claim 5, wherein the firstprocessing circuitry is micro-architecturally different to the secondprocessing circuitry such that performance of the first processingcircuitry is different to performance of the second processingcircuitry.
 7. The data processing apparatus according to claim 1,wherein the destination processing circuitry also comprises a cache. 8.The data processing apparatus according to claim 7, wherein the snoopeddata values retrieved for the destination processing circuitry by thecache snooping circuitry are stored in the cache of the destinationprocessing circuitry.
 9. The data processing apparatus according toclaim 1, wherein the power control circuitry is configured to place thesource processing circuitry, other than the cache, in the power savingcondition during the snooping period, and to place the cache of thesource processing circuitry in the power saving condition following theend of the snooping period.
 10. The data processing apparatus accordingto claim 9, wherein the cache of the source processing circuitry is partof a cache hierarchy within the source processing circuitry, and duringthe snooping period the cache is maintained in the powered state whileat least one other cache in the cache hierarchy is in the power savingstate.
 11. The data processing apparatus according to claim 10, whereinthe cache of the source processing circuitry is a level two inclusivecache which is configured to store all of the data stored in at leastone level one cache of the cache hierarchy.
 12. The data processingapparatus according to claim 1, wherein the power control circuitry isconfigured to maintain the source processing circuitry in the poweredcondition during the snooping period and to place the source processingcircuitry, including the cache, in the power saving condition followingthe end of the snooping period.
 13. The data processing apparatusaccording to claim 12, wherein the cache of the source processingcircuitry is a level one cache.
 14. The data processing apparatusaccording to claim 1, wherein the source processing circuitry isconfigured to perform a cleaning operation on the cache of the sourceprocessing circuitry to write back any dirty data from the cache to ashared memory following the end of the snooping period and before thepower control circuitry places the cache of the source processingcircuitry in the power saving condition.
 15. The data processingapparatus according to claim 1, wherein the destination processingcircuitry is in the power saving condition before the occurrence of thetransfer stimulus and the power control circuitry is configured to placethe destination processing circuitry in the powered condition inresponse to the transfer stimulus.
 16. The data processing apparatusaccording to claim 7, wherein the destination processing circuitry isconfigured to invalidate the cache of the destination processingcircuitry before the destination processing circuitry starts performingthe transferred processing workload.
 17. The data processing apparatusaccording to claim 16, wherein the source processing circuitry isconfigured to continue performing the processing workload while thecache of the destination processing circuitry is being invalidated, andthe workload transfer controller is configured to transfer theperformance of the processing workload to the destination processingcircuitry after the cache of the destination processing circuitry hasbeen invalidated.
 18. The data processing apparatus according to claim1, wherein the snooping period begins when the destination processorstarts performing the processing workload.
 19. The data processingapparatus according to claim 1, wherein the snooping period ends on theoccurrence of any one of a set of snoop stop events comprising at leastone snoop stop event.
 20. The data processing apparatus according toclaim 19, wherein the cache snooping circuitry is configured to monitorwhether any of the set of snoop stop events has occurred.
 21. The dataprocessing apparatus according to claim 19, wherein the at least onesnoop stop event includes an event that occurs when the percentage ofsnoops performed by the cache snooping circuitry that result in a cachehit in the cache of the source processing circuitry drops below apredetermined threshold level.
 22. The data processing apparatusaccording to claim 19, wherein the at least one snoop stop eventincludes an event that occurs when the destination processing circuitrycompletes a predetermined number of processing transactions of apredetermined type.
 23. The data processing apparatus according to claim19, wherein the at least one snoop stop event includes an event thatoccurs when a predetermined number of processing cycles have elapsedafter the destination processing circuitry starts performing thetransferred processing workload.
 24. The data processing apparatusaccording to claim 19, comprising a shared memory shared between thefirst and second processing circuitry; wherein the at least one snoopstop event includes an event that occurs when a particular memory regionof the shared memory is accessed for the first time by the destinationprocessing circuitry after starting performance of the transferredprocessing workload.
 25. The data processing apparatus according toclaim 19, comprising a shared memory shared between the first and secondprocessing circuitry; wherein the at least one snoop stop event includesan event that occurs when a particular memory region of the sharedmemory, which is accessed by the destination processing circuitry for aninitial period after starting performance of the transferred processingworkload, is not accessed by the destination processing circuitry for apredetermined period.
 26. The data processing apparatus according toclaim 19, comprising a shared memory shared between the first and secondprocessing circuitry; wherein the at least one snoop stop event includesan event that occurs when the destination processing circuitry writes toa predetermined memory location of the shared memory for the first timeafter starting performance of the transferred processing workload. 27.The data processing apparatus according to claim 1, comprising a snoopoverride controller responsive to a snoop override condition to overridesnooping of the cache of the source processing circuitry by the cachesnooping circuitry and to control the power control circuitry to placethe source processing circuitry, including the cache, in the powersaving state after the transfer of the performance of the processingworkload without waiting for the end of the snooping period.
 28. Thedata processing apparatus according to claim 27, wherein the snoopoverride condition occurs when the data in the cache of the sourceprocessing circuitry is not required for the destination processingcircuitry to perform the transferred processing workload.
 29. The dataprocessing apparatus according to claim 1, wherein the cache snoopingcircuitry comprises a coherent interconnect coupled to the firstprocessing circuitry and the second processing circuitry.
 30. A dataprocessing apparatus comprising: first processing means for performingprocessing and second processing means for performing processing, thefirst processing means and second processing means being configured toperform a processing workload such that the processing workload isperformed by one of the first processing means and the second processingmeans at a time; power control means for independently controlling thepower supply to the first processing means and the second processingmeans; workload transfer control means for, in response to a transferstimulus, controlling a transfer of performance of the processingworkload from a source processing means to a destination processingmeans prior to the source processing means being placed in a powersaving condition by the power control means, the source processing meansbeing one of the first and second processing means and the destinationprocessing means being the other of the first and second processingmeans; wherein: at least the source processing means has a cache meansfor storing cached data values; the power control means is configured tomaintain at least the cache means of the source processing means in apowered condition during a snooping period following the start ofperformance of the transferred processing workload by the destinationprocessing means; the data processing apparatus comprises cache snoopingmeans for snooping data values in the cache means of the sourceprocessing means during the snooping period, and retrieving the snoopeddata values for the destination processing means; and the power controlmeans is configured to place said at least the cache means of the sourceprocessing means in the power saving condition following the end of thesnooping period.
 31. A data processing method for an apparatuscomprising first processing circuitry and second processing circuitryconfigured to perform a processing workload such that the processingworkload is performed by one of the first processing circuitry and thesecond processing circuitry at a time; the method comprising: performingthe processing workload with a source processing circuitry, the sourceprocessing circuitry being one of the first and second processingcircuitry and comprising a cache, the other of the first and secondprocessing circuitry being a destination processing circuitry; inresponse to a transfer stimulus, transferring performance of theprocessing workload from the source processing circuitry to thedestination processing circuitry prior to the source processingcircuitry being placed in a power saving condition; maintaining at leastthe cache of the source processing circuitry in a powered conditionduring a snooping period following the start of performance of thetransferred processing workload by the destination processing circuitry;during the snooping period, snooping data values in the cache of thesource processing circuitry and retrieving the snooped data values forthe destination processing circuitry; and placing said at least thecache of the source processing circuitry in the power saving conditionfollowing the end of the snooping period.
 32. A data processingapparatus comprising: first processing circuitry and second processingcircuitry configured to perform a processing workload such that theprocessing workload is performed by one of the first processingcircuitry and the second processing circuitry at a time; a workloadtransfer controller responsive to a transfer stimulus to control atransfer of performance of the processing workload from a sourceprocessing circuitry to a destination processing circuitry prior to thesource processing circuitry being placed in a power saving condition bythe power control circuitry, the source processing circuitry being oneof the first and second processing circuitry and the destinationprocessing circuitry being the other of the first and second processingcircuitry; wherein: at least the destination processing circuitry has acache; the destination processing circuitry is configured to invalidatethe cache of the destination processing circuitry before the destinationprocessing circuitry starts performing the transferred processingworkload; the source processing circuitry is configured to continueperforming the processing workload while the cache of the destinationprocessing circuitry is being invalidated; and the workload transfercontroller is configured to transfer the performance of the processingworkload to the destination processing circuitry after the cache of thedestination processing circuitry has been invalidated.